-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Rename files about error codes #60025
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
cc @rust-lang/wg-diagnostics @GuillaumeGomez |
At a quick glance, you may need to change this line in tidy. It appears as if it looks for a |
This comment has been minimized.
This comment has been minimized.
Well, looks good to me (renaming to |
Thank you @davidtwco! It seems good, I changed file name in tidy. |
@JohnTitor |
@petrochenkov I pushed some commits. |
@bors r+ |
📌 Commit a1d2f72 has been approved by |
Rename files about error codes fixes #60017 This PR will be failed in tidy. <details> <summary>The log is here:</summary> ``` tidy check tidy error: duplicate error code: 411 tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:83: __diagnostic_used!(E0411); tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:84: err.code(DiagnosticId::Error("E0411".to_owned())); tidy error: duplicate error code: 424 tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:90: debug!("smart_resolve_path_fragment: E0424, source={:?}", source); tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:92: __diagnostic_used!(E0424); tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:93: err.code(DiagnosticId::Error("E0424".to_owned())); some tidy checks failed ``` </details> I'd like to fix this but I don't know what to do. I will work on later. Please let me know if you have any solutions. r? @petrochenkov
☀️ Test successful - checks-travis, status-appveyor |
fixes #60017
This PR will be failed in tidy.
The log is here:
I'd like to fix this but I don't know what to do.
I will work on later. Please let me know if you have any solutions.
r? @petrochenkov